<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2017 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2017/08-August/02.xhtml" />
		<title>Live website updates are back &lt;https://y.st./en/weblog/2017/08-August/02.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2017/08-August/02.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2017/08-August/01.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2017/08-August/03.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1>Live website updates are back</h1>
			<p>Day 00879: Wednesday, 2017 August 02</p>
		</header>
<section id="general">
	<h2>General news</h2>
	<p>
		<a href="https://wowana.me./">Opal</a> contacted me.
		She reconfigured her onions a while back, which is what cut me off from updating this website.
		She found one of my attempts to connect in an email from her server though, and reached out to me, telling e how to get back in.
		It seems she applied a Let&apos;s Encrypt certificate to my website as well, so now I don&apos;t have to do that.
		I&apos;m not sure if she&apos;s maintaining it, but my plan had been to put it in place and let it expire.
		Maintained or unmaintained, it&apos;ll serve my purpose.
		I also mentioned being banned from #Volatile, and she explained about a whitelist.
		Anyone not on it can&apos;t get in; I now have access.
	</p>
	<p>
		My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
	</p>
</section>
<section id="mental">
	<h2>Mental health watch</h2>
	<p>
		At work today, I noticed that I was calm and mildly happy.
		More happy than I normally would&apos;ve been, given the panic rush coursework morning I had and the rush at work that forced me to stay almost an hour late.
		I think I&apos;ve found my happy place again.
		I don&apos;t have that same euphoria as before, but that probably couldn&apos;t last.
		People don&apos;t walk around in a constant state of euphoria.
		However, it was like none of the little things even mattered and it&apos;d take something rather significant to dampen my mood.
		I think I&apos;m in a state of wholeness once more.
	</p>
	<p>
		It&apos;s interesting to note that when I reach this state, my desire for pair bonding plummets.
		Last time, I remember being just thrilled to be me and thinking I don&apos;t even need a partner.
		Now, the desire for a partner is once more gone.
		I think if a potential partner that seems compatible with me comes my way, I&apos;ll pursue.
		However, it&apos;ll be more out of curiosity than a burning desire.
		I think pair bonding is something I&apos;d like to try, even if only once.
		In fact, curiosity is the <strong>*only*</strong> thing drawing me to the idea of a relationship at the moment.
		There&apos;s no more desire for cuddling.
		I guess cuddling would be okay, but I&apos;m back to thinking it&apos;d be kind of weird.
		There&apos;s no more desire for sex, either.
		Sex actually seems mildly repulsive now, though nowhere near as repulsive as it seemed to me before my sexuality awakened.
	</p>
	<p>
		To be honest, I&apos;m also curious about how a breakup would affect me.
		I wouldn&apos;t want to intentionally and artificially cause one; I&apos;m not <strong>*that*</strong> curious.
		However, I kind of wonder based on the language people choose to use whether I&apos;d be hit that hard by it.
		People say that they&apos;re completed by their partner and that their partner is a part of them.
		I&apos;ve always rejected such language, as it seems self-deprecating.
		It makes it seem that the person is incomplete and unwhole on their own; that they&apos;re a partial person.
		Once my sudden gayness struck though, I understood the language.
		I <strong>*did*</strong> feel incomplete.
		I <strong>*did*</strong> feel unwhole.
		So is this why breakups hurt so much?
		Is it because one feels a loss of their completeness?
		If so, I might not be hurt that badly.
		That said, this is a wild stab in the dark on my part.
		Maybe breakups would hurt me as much as anyone else.
		In the name of science though, I&apos;m firmly placing potential breakups on the list of reasons for me to <strong>*find*</strong> a relationship, not <strong>*avoid*</strong> one.
		I&apos;m still avoiding any relationship that seems doomed from the start though.
		I can&apos;t live with a smoker, I can&apos;t have sex with a woman, et cetera.
		I will do what I can to make a relationship successful, but if it fails, that&apos;ll be a new experience for me.
	</p>
</section>
<section id="university">
	<h2>University life</h2>
	<p>
		I finished up my discussion assignment for the week:
	</p>
	<blockquote>
		<p>
			Dividing up responsibilities like that serves some very important functions.
			First, it makes reuse of components much easier.
			Second, it prevents bloat, especially with reused components.
			Third, it makes it easy to debug.
			If something fails, you can usually track it down to which component is causing the problem based on what the problem is.
			If not, you can at least find the chain of components the problem is in, and rule out all other components.
			That narrows down your search space significantly so you can find and repair the bug efficiently.
			And fourth, it allows different developers to work on different components without interfering with each other&apos;s development.
			It&apos;s like UNIX people say: do only one thing and do it well.
		</p>
	</blockquote>
	<blockquote>
		<p>
			After reading everyone else&apos;s posts, I think I was wrong about what the model is.
			I thought it was the full back end, including both data manipulation and data storage, but it looks like that might not be right.
			I guess the data manipulation really is part of the controller then.
			My bad.
		</p>
	</blockquote>
	<blockquote>
		<p>
			You make a good point about the separation preventing interference.
			As things are modified and updated, interference between unrelated tasks becomes a real issue if code is all tangled up.
			Each task should be decoupled from the rest of the application as much as is feasible to allow for the most flexibility.
			Something does need to exist to tie everything together, but that should be minimal, if possible.
		</p>
	</blockquote>
</section>
		<hr/>
		<p>
			Copyright © 2017 Alex Yst;
			You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F08-August%2F02.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F08-August%2F02.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>

